Policy based information lifecycle management

ABSTRACT

A method, article of manufacture, and apparatus for managing a lifecycle of an auditory communication is disclosed. In an embodiment, this comprises receiving an auditory communication with associated data representing identified keywords in the communication and call transport information. A data for a disposition of the communication is determined from a portion of the identified keywords, a portion of the call transport information, or a portion of the policies invoked. The communication is associated with the date(s).

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of co-pending U.S. patent applicationSer. No. 10/884,345, entitled METHOD AND SYSTEM FOR INFORMATIONLIFECYCLE MANAGEMENT filed Jul. 1, 2004 which is incorporated herein byreference for all purposes. This application is related to co-pendingU.S. patent application Ser. No. 10/884,453 for METHOD AND SYSTEM FORPROCESSING AUDITORY COMMUNICATIONS, filed Jul. 1, 2004, which isincorporated herein by reference for all purposes; U.S. patentapplication Ser. No. 10/884,477 for MESSAGE INDEXING AND ARCHIVING,filed Jul. 1, 2004, now U.S. Pat. No. 7,330,536, which is incorporatedherein by reference for all purposes; U.S. patent application Ser. No.10/884,473 for AUTOMATED CALL MANAGEMENT, filed Jul. 1, 2004, now U.S.Pat. No. 7,457,396, which is incorporated herein by reference for allpurposes.

FIELD OF THE INVENTION

This invention relates generally to auditory communications. Moreparticularly, processing, archival, and management of auditorycommunications is disclosed.

BACKGROUND OF THE INVENTION

Companies, particularly in the finance, insurance, and healthcarefields, record some or all of the telephone conversations between theiremployees and their clients for evidence in case of a dispute. Forexample, a stock brokerage company may record thousands of conversationsa year, mainly the details of customer transactions conducted over thetelephone, to ensure that the execution of the customers' orders areconsistent with the customers' spoken orders. It has become increasinglyimportant for corporations to keep track of communications betweenemployees and between employees and the corporation's customers and/orthe public. The requirements of the SEC, NASD, HIPAA, Sarbanes-Oxley Actof 2002, and various anti-harassment and anti-discrimination laws putfurther pressure on corporations to have the ability to monitor, record,archive, index, retrieve, and control employee communications.

Traditionally, such conversations are recorded as voice/sound recordingson various recording media. Such conversations can also then beassociated with individual customer records and retrieved if necessary.Recently, compression techniques have been put to use in order todecrease the amount of recording media required to capture and archivesuch recordings.

Voice data presents many challenges and problems to companies who planto use it for reasons of compliance and content control. In order tolocate recordings of telephone conversations with potentiallynon-compliant language, it would require near real-time playback whilesomeone listens for the non-compliant language. It also makes it verydifficult to monitor or identify compliance violations prior to acomplaint. In the case of a complaint, the complainant would provide theapproximate time and date which would narrow the scope of the search.Monitoring conversations for non-compliant language requires nearreal-time monitoring of all conversations. This takes considerable time,effort and cost.

It is very difficult for companies to keep track of employee telephoneconversations because telephone conversations have substantial storagerequirements and are difficult and time consuming to analyze fornon-compliant communication and language, or a particular communication.

Many companies now use Voice over Internet Protocol (VoIP) networks toplace and receive telephonic communications rather than solely using thetraditional Public Switched Telephone Network (PSTN.) In VoIP networks,telephone voice conversations are converted to data that is compatiblewith IP networks. Once converted, the data can be switched and routed asany network data. When conversations are recorded, they are stored asvoice messages that must be processed manually to determine whether theycontain non-compliant communication and language, or a particularcommunication. Such processing is expensive and time-consuming,requiring considerable human intervention.

There is a need, therefore, for an improved method, article ofmanufacture, and apparatus for monitoring, recording, archiving,indexing, retrieving, processing, and managing communications in theform of voice messages.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention will be readily understood by the followingdetailed description in conjunction with the accompanying drawings,wherein like reference numerals designate like structural elements, andin which:

FIG. 1 is a diagram of a voice message processing system being used witha VoIP network;

FIG. 2 is a flowchart illustrating operation of the voice messageprocessing system;

FIG. 3 is a flowchart illustrating processing of an auditorycommunication using policies;

FIG. 4 is a flowchart illustrating processing of an auditorycommunication and using metadata to track matched keywords;

FIG. 5 is a flowchart illustrating archival of an auditorycommunication;

FIG. 6 is a flowchart illustrating the operation of policies, keywords,and metadata to process auditory communications;

FIG. 7 is a flowchart illustrating the use of dates to controlpost-storage processing of an auditory communication;

FIG. 8 is a flowchart illustrating call management;

FIG. 9 is a table illustrating inbound call processing; and

FIG. 10 is a table illustrating outbound call processing.

DESCRIPTION OF THE INVENTION

A detailed description of one or more embodiments of the invention isprovided below along with accompanying figures that illustrate theprinciples of the invention. While the invention is described inconjunction with such embodiment(s), it should be understood that theinvention is not limited to any one embodiment. On the contrary, thescope of the invention is limited only by the claims and the inventionencompasses numerous alternatives, modifications, and equivalents. Forthe purpose of example, numerous specific details are set forth in thefollowing description in order to provide a thorough understanding ofthe present invention. These details are provided for the purpose ofexample, and the present invention may be practiced according to theclaims without some or all of these specific details. For the purpose ofclarity, technical material that is known in the technical fieldsrelated to the invention has not been described in detail so that thepresent invention is not unnecessarily obscured.

It should be appreciated that the present invention can be implementedin numerous ways, including as a process, an apparatus, a system, adevice, a method, or a computer readable medium such as a computerreadable storage medium or a computer network wherein programinstructions are sent over optical or electronic communication links. Ageneral purpose computer system such as an Intel-based processor runningMicrosoft Windows or Linux may be used, or a specialized appliance couldbe used. In this specification, these implementations, or any other formthat the invention may take, may be referred to as techniques. Ingeneral, the order of the steps of disclosed processes may be alteredwithin the scope of the invention.

An embodiment of the invention will be described with reference to avoice message processing system, but it should be understood that theprinciples of the invention are not limited to voice messages. Rather,they are applicable to any auditory communication capable of conveyingmeaning. Further, they are not limited to communications consistingsolely of auditory communications, but can be used with anycommunication comprising an auditory component, including but notlimited to videoconferences, video broadcasts, radio broadcasts, cellphone communications, wired communications, VoIP-based communications,digital communications, analog communications, and video-phonecommunications. Although the concepts herein are described with respectto a VoIP network, it should be understood that they are not limited toa VoIP network. Rather, they are applicable to any network ortransmission means capable of conveying auditory communication, such asPSTN (Public Switched Telephone Networks) and POTS (Plain Old TelephoneService) services, and such communication may be conveyed in analog ordigital form.

Disclosed herein are a method and system to comprehensively monitor,record, archive, index, retrieve, perform auditory data-to-textprocessing, control data representing auditory communications made overa communication connection and their control data, consolidation andcontrol of these data with other communications made to and from thesame entity, and to manage the ultimate disposition of the archived andlive communications. In particular, the foregoing will be described withrespect to a VoIP network conveying auditory communications in the formof telephone conversations (calls). The method comprises receiving VoIPdata from the network representing the telephone conversation and thecontrol elements of the connection and performing a series of optionalprocesses on the data in order to monitor its content (its linguisticmeaning), record the data, archive the recorded data, index the contentof the conversation, retrieve the recorded data from the archive, andcontrol the progress of the data traffic that supports the telephoneconversation (e.g., terminate a call if a non-compliant conversation istaking place or if communication with an unauthorized person or entityis attempted). Such a solution makes use of network-data-to-textprocessing for identification of key words or phrases and/or forconversion of the entire data set/traffic representing telephoneconversations into text.

FIG. 2 illustrates the method. The method may be implemented in anetwork appliance system configured to identify VoIP network traffic,step 100, determine the course of action(s) to be performed on the VoIPtraffic based on predefined or dynamic policies, step 102, receive VoIPnetwork data representing the voice and control portions of thetelephone conversation, step 104, clone or “tap” the data so that theflow of data between source and destination is unimpeded or trap thetraffic and perform further processing before permitting its passageand/or cloning, step 106, and store the data in its native format or inany other changed format to a storage medium together with otherrelevant information (such as source IP address, destination IP address,time, date, caller ID, agent ID, duration of call, location of agent,location of caller, station ID, etc.), step 108.

The system may scan the network data representing the voice portion ofthe network traffic for the presence or absence of keywords and/orphrases through a network-data-to-text processing system, step 110, orconvert the entire data set/traffic representing telephone conversationsinto text, optionally index the recorded data and the associated text(“Conversation Text”) from the network-data-to-text process, store thetext from the network-data-to-text process, and compare the ConversationText to a predefined lexicon of words and/or phrases. Based on positivematches and/or negative matches (lack of match), the system may takespecific action as determined by the appropriate policy, step 112. Thismay also be determined by reference to control data. For example, suchactions include but are not limited to termination of the call,notification of specific third parties, dynamic connection with andintervention of third parties and so on. Some or all of the foregoingelements may be utilized in accordance with the principles of theinvention. The system may compare the data to a lexicon containingauditory representations of words directly, without first converting theentire data set/traffic into text.

This approach provides complete control, recording, archiving,retrieval, and analysis of VoIP network traffic. It also provides ameans of associating VoIP network traffic with communications made usingother media such as email, instant messenger, etc. by the same parties.

In an embodiment, a voice message processing system is used to processauditory communications in the form of telephone calls. The voicemessage processing system may comprise a processor in the form of acomputer system, configured to receive voice messages from a source ofvoice messages, such as telephone system, a voice mail system, or a linemonitor. Multiple network interface cards may be used to connect thevoice message processing system to the VoIP network. The voice messageprocessing system may be integrated with the function of the VoIPsystem/gateway, or be a standalone system to which the VoIP systempasses data. The voice message processing system may be attached to theVoIP network and its functionality invoked when explicitly instructed bya user/administrator or system-based policy. This may be addedexternally to VoIP systems or made an integral element of a VoIP system.

A variety of methods for intercepting and/or monitoring calls may beused, to give the voice message processing system access to the callcontent. The voice message processing system may be configured tooperate and perform its functions at the point in the network where allVoIP traffic is processed such as the VoIP gateway, gatekeeper, server,and/or switch. This central point provides access to all VoIP trafficregardless of their source or destination (i.e. internal and externalcalls can be processed).

FIG. 1 illustrates an embodiment of a voice message processing system inuse with a VoIP system. Voice message processing system 10 is connectedto a VoIP gateway 20. VoIP gateway 20 may be a gateway, server, switch,or other point through which VoIP traffic passes. Voice messageprocessing system 10 is connected to VoIP devices 30, which may betelephones or other devices that communicate via VoIP. Storage device 40is attached to voice message processing system. There may be more thanone VoIP gateway 20 connected to voice message processing system 10, andthere may be more than one voice message processing system 10. Voicemessage processing system 10 may be combined with VoIP gateway 20.Multiple connections may be used between the various elements in FIG. 1,though single lines are shown for brevity. Storage device 40 maycomprise multiple storage devices, and may be connected to the networkrather than directly attached to voice message processing system 10.

In this configuration, the voice message processing system is inlinewith the flow of VoIP traffic to the central VoIP handling system (suchas the VoIP gateway/server/switch). This configuration may be added toVoIP systems through external means without change to the VoIP system,other than the addition of the voice messaging system inline with theflow of VoIP data. VoIP data may be identified by scanning the headersof IP packets on the network, or by knowing the IP address, MAC address,or port of the various VoIP devices on the network and scanning packetsgoing to and from those devices. A VoIP network switch may be configuredto send a duplicate copy of a communication stream to the voice messageprocessing system, while permitting the original communication stream tocontinue to its destination, thus cloning or “tapping” the data stream.The duplication of IP packets can be done either in hardware orsoftware. The switch may also be configured to redirect the originalcommunication stream to the voice message processing system, which maypass the original communication stream to its destination afteranalyzing and processing it.

Call setup metadata may be passed to the voice message processingsystem, and this metadata may vary depending on the call transportmethod. The call transport information may include information such asAutomatic Number Identification (ANI) of the calling party, Station ID,time of day, call time (elapsed time), User ID, transport protocol,trunk ID, line ID, Class of Service, Quality of Service, Source Address(SA), Destination Address (DA), etc.

The voice message processing system identifies keywords within a call,in order to generate additional metadata that provides additionalinformation and characterization of the content of the call. A keywordis an auditory element or representation of an audio element, textelement, or both, and may be a spoken word or utterance but is notlimited to speech. The keyword may be found in a lexicon kept by thesystem, and more than one lexicon may be used by the system. Althoughseveral lexicons may be used, it should be understood that they may bereferred to collectively as constituting a single lexicon. The keywordidentification can be done by the system itself or an ancillary systemin communication with the voice message processing system. AutomaticSpeech Recognition (ASR) systems attempt to provide a completetranscription of a call through the use of Speech-to-Text (STT)technology which renders the entire call content (when it comprisesspeech) into text. The keyword may be directly derived from the calldata or extracted from the rendered text.

The performance of keyword/phrase scanning and/or speech-to-textprocessing can be optionally performed in real-time or deferred forlater processing. This would be determined by policy or administratorsettings/preferences. For purposes of review for accuracy, theconversation text and telephone recording can be indexed to each other.In this way, a comparison can be made between the recording and theconversation text. A signature (hash or hash digest) of the text,recording, and metadata may also be added to the metadata for purposesof non-repudiation.

Referring now to FIG. 3, an embodiment of the process can be describedas follows: receive the call and its call setup (transport) metadata,which may include caller ID, station ID, line, time of day, etc., step113. Based on the metadata, select the applicable policy, step 114. Thepolicy is applied in step 115. This may include selecting the lexicon(s)to be used in analyzing the call content. Using the keywords from thelexicon(s), search the call and identify any keywords that are present,step 116. In step 117, action is taken in accordance with any policiesinvoked by the keyword matches and/or non-matches. These actions mayinclude archiving the call, loading additional policies/lexicons forfurther analysis, adding a third party (person or system) to the call,terminating the call, adjusting the characteristics of the call,creating metadata describing call content, policies invoked, and actionstaken, etc.

In an embodiment, shown in FIG. 4, rather than attempting to render thecall content to text or perform a STT process to render the call'scontent to text, the voice message processing system may listen to thecall's content, step 120, and compare the content to a list of elementsspecified in a lexicon that comprises a group of data elementsconsisting of auditory elements or representations of audio elements(keywords) associated to text or other data elements, step 122. Upondetection of call content that matches lexicon content, step 124,metadata may be generated in step 126 and associated with the callcontent in step 128. Such metadata may be the text equivalent of theauditory content or it may be a pointer to other data held within thelexicon.

The system can search for keywords in the auditory communication thatpositively match keywords in the lexicon. The search for keywords withina call may further specify:

-   -   The order of the appearance/sequence (e.g., “Buy” followed by        “Stock”)    -   Specific inter-keyword distance (“Buy” followed by “Stock” as        the next word)    -   The number of repetitions within a timeframe or communication        session    -   The inverse of the above:        -   Keywords are present but not in the specific sequence        -   Keywords are present but not within the inter-keyword            distance        -   Keywords are present but not repeated within specification    -   The absence of the keyword(s); i.e. a non-match or negative        match    -   Groups of keywords

Keywords (including the tests described herein) may be used to determinewhether the call should be archived, to determine whether the call isviolating a compliance policy such as Sarbanes-Oxley and if a prescribedaction should be taken, and to affect changes to the progress and/orcontrol of the call and/or the call's characteristics. Metadata such asthe call setup metadata may be used in conjunction with the keywords todetermine what actions to take. This may be defined through the use oftriggering policies, which identify the criteria upon which a set ofactions or policies should be executed or invoked. The voice messageprocessing system can be configured to chain policies together. Policiesmay be dynamic; i.e, a policy may be invoked by another policy.

For example, metadata might indicate that a call is a customer servicecall. This would trigger a policy for handling customer calls. Thecompany might have a requirement that all customer servicerepresentatives say “Thank you for calling XYZ. We appreciate yourbusiness.” A negative match may be used to determine when arepresentative is not in compliance with this requirement (i.e. neglectsto thank the customer for calling and express appreciation). If anegative match is found, another policy may be invoked to archive thecall and flag it for review by a supervisor. This system could be usedto alleviate the need for constant monitoring of phone calls bysupervisors.

In an embodiment, if the voice message processing system determines thata call contains certain keywords, it may activate a policy that requiresarchiving of the call, and also activate a policy that requiresarchiving all subsequent calls between that caller and called party forthe next 30 days. The system may also track information from one call toanother, such as determining that a caller frequently uses certainkeywords in every call. Thus, if a caller frequently said “buy stock” or“dump stock” in several consecutive phone calls, this pattern could beflagged for review by the voice message processing system.

Archiving the call is shown in FIG. 5. If the voice message processingsystem determines from the keywords that the call should be archived, itcan store the call on its storage device 40, step 130, or direct thecall content to a voicemail system for storage. The voice messageprocessing system may store the associated metadata with the call, step132. The metadata may be used in machine-assisted searches to identifyand retrieve archived calls that match desired parameters. Thus, thevoice message processing system may be used to identify keywords in acall, and based on the presence of those keywords and possibly theassociated metadata, determine that a call is to be archived somewhere.Metadata indicating the presence and frequency of the identifiedkeywords would be included with the archived call to facilitate latersearch and retrieval, step 134. The metadata could contain pointers tothe keywords in the lexicon, or the metadata could contain the keywordsthemselves.

In an embodiment, the call may be archived with metadata indicatingwhich policies were triggered, step 136, such as by including the policyID, the policy signature (hash), message signature (hash), index, orpointers to specific elements within the policy that are applicable tothe triggering message. A policy may be invoked more than once, and itsfrequency of invocation could be recorded in the metadata. Othermetadata may also be included, such as the caller ID, the called partyID, the time and date the message was received, inspected, or forwarded,and message length. Also included may be a hyperlink, pointer, or indexthe keywords into corresponding parts of the recorded call to thekeywords and relevant portions of the call, step 138.

The recording media for archival may be selected by theuser/administrator or policy. For example, VoIP network data (includingthe call), metadata, and call text (if any) may be recorded to “writeonce read many” (WORM) media, re-recordable media, erasable media, solidstate recording media, etc. EMC Centera, available from EMC Corporation,is a magnetic disk-based WORM device that is well-suited for storingsuch data. Selection of media and location of the media are determinedby the requirements of the user/administrator and the purpose of therecording. In cases of compliance issues where the recordings are usedfor legal purposes such as evidence in a court of law, the media chosenwould be specified by law. In these cases, nonvolatile, write once mediathat reside at an off-site location (possibly stored with a third partyacting as an escrow agent) may be used. The user/administrator or policycan specify multiple and varied forms of media. The various types ofcall metadata may be stored on separate storage devices from the callcontent itself, step 140.

The voice message processing system is not limited to the specificexamples of architecture of the network-data-to-text processing systemor the storage system used for the voice and text data. It is applicableto tape storage and all other data storage devices.

All calls may be archived automatically, and the voice messageprocessing system could store any identified keywords with each call toindicate that those keywords were found in that call.

Other call processing may be performed together with or separately fromarchival. For example, a call may be quarantined when keywords areidentified that are predefined as requiring additional analysis. Thecall may be archived with metadata indicating the presence of thekeywords and that the recorded call is classified as a quarantine call.This decision may be based solely on the presence of the keywords, or itmay take into account call setup metadata such as the identity of thecalling party or identity of the called party.

An embodiment is illustrated in FIG. 6. A call and its call transportmetadata are received in step 150, and policies are invoked based on themetadata, step 152. This may include selecting a lexicon or group oflexicons to use. The call is compared to the lexicon to determinewhether positive or negative matches to the keywords are present in thecall, step 154. The policies are used to determine the proper actionbased on the positive and negative matches found, step 156. Thespecified action may include searching for additional keywords in thecall. Policies may be invoked by the resulting positive and/or negativematches, and their specified actions executed (such as quarantining thecall), step 158.

Upon a call's classification as a quarantine call, a human operator ormachine system may be notified, and the call may be made available forfurther analysis and processing. For example, a call containing keywordsthat trigger quarantine could be routed to a human operator forlistening in real time, while the call is still taking place. This wouldrequire the voice message processing system to be processing live calls.

Additional metadata regarding the notification is created and added tothe quarantined call's metadata, such as the date of notification,required response time/date, triggering policy and keywords, message ID,identity of the notified parties, etc. As the quarantined call isprocessed through a work flow (for review, approval, etc.), theassociated metadata is appended to the quarantined call's metadata andretained until a defined expiration date, if any.

The voice message processing system can be configured to retain archivedand quarantined calls until a specified disposition date, which may bedetermined by keywords identified in the call or policies invoked by thecall. An embodiment is illustrated in FIG. 7. For example, after thesystem receives the call, step 160, a routine call might be retained for90 days, but if the call contains certain triggering keywords ortriggers certain policies, the call might be retained for seven years.Metadata relating to call transport may also be used by the system todetermine the disposition and disposition date. Step 162. Thedisposition(s) and disposition date(s) may be stored with the call orseparately from the call, step 164. Upon reaching the disposition date(or expiration date), the stored call and associated metadata may bepartially or completely destroyed, step 166. Other types of processingand disposition may be invoked upon reaching the expiration date, suchas hierarchical storage management functions (e.g., moving the data fromdisk drive media to optical or tape media), bit rate, encryption,application of digital rights management services, service levelagreements, and other services associated with information lifecyclemanagement. This processing may be performed by the voice messageprocessing system or other system.

The quarantine function may be used to pro-actively monitor calls forviolations of Sarbanes-Oxley, HIPAA, SEC, NASD, corporate, and otherlaws, regulations, and policies. For example, if a call contained thewords “buy” and “stock” within one word of each other, the call would bequarantined with metadata indicating that the words “buy” and “stock”were found in the call within one word of each other.

Call control is based on identifying, in real-time (during the call),the presence or absence of keywords triggering specific policies thatresult in actions that control the call's characteristics and handling.As the call is in progress, the voice message processing system mayremain active and listen for specific keywords that are associated withactions other than archive and quarantine. Such actions may control theprogress, quality, and characteristics of the call. For example, if anyof the call parties say the keywords “I can't hear you,” a policy couldactivate an action which would signal the calling system equipment toincrease the volume of the auditory portion of the call, changecommunications channels, increase bandwidth allocated to the call, alterthe transport (intermediate routing) of the call, or take other measuresto improve the auditory quality of the call.

Specific keywords can be known by the callers and deliberately spoken inorder to invoke a desired policy. For example, the caller could say,“Operator, call Bob Smith,” and the policy that is triggered by thekeywords initiates actions that cause the calling equipment to add therequested party to the call. Other examples of call control aretermination of the call, conferencing other parties to the call,encryption of the call, dropping specific parties from the call,accessing the public announcement system, adding a human or machinemonitor to the call, etc. Call control can also be used to intentionallyinvoke a recording of the call (example: the caller says, “Operator,record this call,” which the voice message processing system identifiesas a request to archive the call.

In an embodiment, call management may entail using the call transportmetadata to trigger a policy, as shown in step 170 in FIG. 8. The policymay identify the lexicon(s) to be used, step 172, and the call iscompared to the lexicon(s) to find keyword matches, step 174. Thekeyword matches (whether positive or negative) are used to invokepolicies, step 176, and the actions specified by the policies areexecuted. One such action might be to begin archiving the call, andcontinue monitoring the call with a new lexicon. In this case, theprocess would loop back to step 172, in which a lexicon is selected, andcall processing could continue as before.

An example of processing an inbound call is illustrated in FIG. 9. Asshown, a call is initiated when the caller goes off-hook. A triggerpolicy is invoked and compared to the available information. The voicemessage processing system obtains certain information such as stationID, line card selected, time of day, and date. This information is usedto determine if a trigger policy is applicable. The trigger policy wouldspecify which policies, if any, are applicable to the call based on theinformation available at that point.

The caller or call recipient may optionally be required to enter his/herID code (PIN) in order to identify himself/herself. Another triggerpolicy is invoked to determine which, if any, policies are applicable.

The call setup is performed, meaning that the caller secures a trunk(outside line) and dials a number or the caller begins dialingimmediately (making an internal call). Based on the information from thecall setup, a trigger policy is invoked, and it is determined whichpolicies are applicable given all of the previous information and thenew information (such as external trunk ID, internal line ID, callerID).

The call commences, meaning that the caller's request to complete theconnection to the called party is attempted. If the call setup issuccessful, the caller and the called party are connected and begintheir communication. The policies affecting the communication sessionare enacted. If the call setup is not successful (such as a busy signalor no answer), the policies that would apply to a successful call setupare not enacted, but the attempt and associated metadata may optionallybe archived.

When the call is disconnected, post-call actions are performed inaccordance with the actions specified in the applicable policies. Forexample, if a call would not normally be archived or quarantined basedon the station ID, caller ID, called party ID, etc., but during the callrestricted speech is used and certain keywords are detected, then thecached call would be quarantined. If no restricted speech was usedduring the call then the call would not be quarantined or archived andthe cache would be cleared (deleted).

The processing of an outbound call is illustrated in FIG. 10. A call isreceived and the phone rings. A trigger policy is invoked and comparedto the available information. The voice message processing systemreceives certain information such as ANI, trunk port, station ID, linecard selected, time of day, and date. This information is used todetermine whether a trigger policy is applicable. The trigger policywould specify which policies, if any, are applicable to the call basedon the information available at that point.

The called party answers the telephone and the call setup is performed.Based on the information from the call setup, a trigger policy isinvoked and it is determined which policies are applicable given all ofthe previous information and the new information (external trunk ID,trunk port, internal line ID, etc.).

The called party may be optionally required to enter his/her ID code(PIN) in order to identify himself/herself. Another trigger policy isinvoked to determine which, if any, policies are applicable.

The call commences, meaning that the caller's request to complete theconnection to the called party is completed. If the call setup issuccessful, the caller and the called party are connected and begintheir communication. The policies affecting the communication sessionare enacted. If the call setup is not successful (such as a busy signalor no answer), the policies that apply to a successful call setup arenot enacted.

The call is disconnected, and post-call actions are performed dependingon the actions specified in the applicable policies. For example, if acall would not normally be archived or quarantined based on the StationID, caller ID, called party ID, etc., but during the call restrictedspeech is used and certain keywords are detected, then the cached callwould be quarantined. If no restricted speech was used during the callthen the call would not be quarantined or archived and the cache wouldbe cleared (deleted).

The voice message processing system may be used in real-time such asduring a call, or applied to recordings of auditory communications. Itis not limited to communication systems utilizing a centralized server,switch, exchange, etc., but may also be used with non-centralized andpeer-to-peer networks and communications. Additionally, the voicemessage processing system can be used to control the flow, routing,bandwidth, CoS, QoS, security, encryption, and duration of calls madevia VoIP systems based on matches to the Lexicon. For example,encryption of the call could be based on the identity of the callparties and matches to the lexicon.

Telephone conversations may be recorded, processed into text(speech-to-text), and then formatted for delivery to an email archiveand management system, such as LEGATO EmailXtender, EmailArchive, orEmailXaminer, available from EMC Corporation, for later retrieval,analysis, and other disposition. The data objects that are held in theEmailXtender/EmailArchive/EmailXaminer system (Legato InformationLifecycle Management System or like system) are voice, the voice-to-texttranscription of the conversation, and other metadata such as thesource/destination information of the caller and called party, stationID, time of call, time of call termination, caller ID, keywords found,etc. The VoIP call data elements (and their derivative elements) may bepackaged in such as way as to make them manageable by email systems andemail management systems such as Microsoft Exchange, Microsoft Outlook,and LEGATO EmailXtender.

The presentation to the user of this information may be through an emailclient application, and have a front-end appearance to the user of anemail message in the Inbox. The relevant call information (text, voicerecording, metadata, etc.) may be contained within this pseudo-message,with hyperlinks or other references to the auditory portions of the callcontaining keywords and relevant portions. The user may use these linksto confirm that certain keywords were found and to understand thecontext (such as to determine whether a law or regulation has beenviolated).

Users and administrators could easily and quickly archive, retrieve,analyze, sort, and filter hundreds of thousands of telephoneconversations in the same manner they handle email messages.

Compared to simply sending a voice recording of a telephone conversationto an email recipient (the recording will be treated by the email serveras an attachment), this approach would allow the system to detect andunderstand that the attachment is a voice recording and process it in acompletely different manner than typical email messages withattachments.

Although the methods and systems herein have been described with respectto an illustrative embodiment, it should be appreciated that the methodsand systems disclosed are independent of the precise architecture of thenetwork-data-to-text processing system or the storage system used forthe voice and text data, and are applicable to tape storage, opticaldevices, and all other types of data storage. The principles are equallyapplicable to VoIP, PSTN, PBX, digital, analog, and all other systemsuseful for auditory communication.

For the sake of clarity, the processes and methods herein have beenillustrated with a specific flow, but it should be understood that othersequences may be possible and that some may be performed in parallel,without departing from the spirit of the invention. Additionally, stepsmay be subdivided or combined. As disclosed herein, software written inaccordance with the present invention may be stored in some form ofcomputer-readable medium, such as memory or CD-ROM, or transmitted overa network, and executed by a processor.

All references cited herein are intended to be incorporated byreference. Although the present invention has been described above interms of specific embodiments, it is anticipated that alterations andmodifications to this invention will no doubt become apparent to thoseskilled in the art and may be practiced within the scope and equivalentsof the appended claims. More than one computer may be used, such as byusing multiple computers in a parallel or load-sharing arrangement ordistributing tasks across multiple computers such that, as a whole, theyperform the functions of the components identified herein; i.e. theytake the place of a single computer. Various functions described abovemay be performed by a single process or groups of processes, on a singlecomputer or distributed over several computers. Processes may invokeother processes to handle certain tasks. A single storage device may beused, or several may be used to take the place of a single storagedevice. The present embodiments are to be considered as illustrative andnot restrictive, and the invention is not to be limited to the detailsgiven herein. It is therefore intended that the disclosure and followingclaims be interpreted as covering all such alterations and modificationsas fall within the true spirit and scope of the invention.

1. A method of managing a lifecycle of an auditory communication havingassociated data representing invoked policies, comprising: determining,from at least one of the invoked policies, a date for a disposition ofthe communication, wherein at least one of the invoked policies includesa policy invoked based on metadata; associating the communication withthe date; and storing the date in a storage device.
 2. The method asrecited in claim 1, further comprising associating the storedcommunication with data indicating keywords present in thecommunication.
 3. The method as recited in claim 2, further comprisingassociating the communication with data indicating call transportinformation.
 4. The method as recited in claim 3, wherein thedisposition to be made is determined from at least one of the invokedpolicies, at least one of the identified keywords, or at least a portionof the data indicating call transport information.
 5. The method asrecited in claim 4, further comprising storing the date with theassociated data.
 6. The method as recited in claim 1, further comprisingassociating the communication with data indicating the disposition to bemade.
 7. The method as recited in claim 6, wherein the disposition to bemade is determined from at least one of the invoked policies.
 8. Themethod as recited in claim 7, further comprising storing the date withthe associated data.
 9. The method as recited in claim 8, furthercomprising storing the communication in a storage device.
 10. The methodas recited in claim 9, wherein the associated data is stored in astorage device.
 11. The method as recited in claim 10, wherein thecommunication and associated data are stored in different storagedevices.
 12. The method as recited in claim 10, further comprisingretrieving the communication and associated data, determining thedisposition to be made, and acting in accordance with the dispositionwhen the date has been reached.
 13. The method as recited in claim 12,wherein the date is an expiration date and the disposition includesdeletion of the communication.
 14. A system for managing a lifecycle ofan auditory communication having associated data representing invokedpolicies, comprising a first storage device and a processor configuredto: determine, from at least one of the invoked policies, a date for adisposition of the communication, wherein at least one of the invokedpolicies includes a policy invoked based on metadata; associate thecommunication with the date; and store the date of disposition on thefirst storage device.
 15. The system as recited in claim 14, wherein thecommunication is stored on a second storage device.
 16. The system asrecited in claim 15, further configured to act on the disposition whenthe date has been reached.
 17. The system as recited in claim 16,wherein the disposition includes deletion, and further configured toremove the stored communication from the second storage device.
 18. Acomputer program product for managing a lifecycle of an auditorycommunication having associated data representing identified invokedpolicies, comprising a computer readable storage medium having machinereadable code embodied therein for: determining, from at least one ofthe invoked policies, a date for a disposition of the communication,wherein at least one of the invoked policies includes a policy invokedbased on metadata; associating the communication with the date; andstoring the date of disposition on a storage device.